Related Issue

Discovered while investigating a user report that starting the TUI shows "Detected install source: unsupported package manager or layout" for a bun global installation.

Problem

With installed kimi cli via bun with newer bun 1.3.x+ layout, the kimi or kimi update throws warning messages for "Detected install source: unsupported package manager or layout" .

Recent versions of bun install global packages under ~/.bun/node_modules/<pkg> and create a shim in ~/.bun/bin/. Kimi Code's install-source detection only recognized the older ~/.bun/install/global/node_modules/<pkg> layout, so bun global installs were misclassified as unsupported. This caused:

• The startup warning Detected install source: unsupported package manager or layout.
• kimi upgrade falling back to a manual npm command instead of using bun add -g.

Both layouts are valid bun global installs and expose the CLI through ~/.bun/bin/:

# Legacy layout expected by the old code
~/.bun/
├── bin/
│   └── kimi -> ../../install/global/node_modules/@moonshot-ai/kimi-code/dist/main.mjs
└── install/global/node_modules/
    └── @moonshot-ai/kimi-code/

# Current layout used by bun 1.3.14+
~/.bun/
├── bin/
│   └── kimi -> ../../node_modules/@moonshot-ai/kimi-code/dist/main.mjs
└── node_modules/
    └── @moonshot-ai/kimi-code/

What changed

• Updated apps/kimi-code/src/cli/update/source.ts so the bun heuristic matches both the legacy .bun/install/global/ path and the current .bun/node_modules/ path.
• Added unit tests in apps/kimi-code/test/cli/update/source.test.ts covering the real-world ~/.bun/node_modules/@moonshot-ai/kimi-code layout.

Checklist

• I have read the CONTRIBUTING document.
• I have linked a related issue, or explained the problem above.
• I have added tests that prove my feature works.
• Ran gen-changesets skill, or this PR needs no changeset.
• Ran gen-docs skill, or this PR needs no doc update.